home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990725-20000114
/
000406_news@columbia.edu _Tue Jan 4 01:52:54 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-01-13
|
6KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id BAA04574
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 4 Jan 2000 01:52:53 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id BAA20672
for kermit.misc@watsun.cc.columbia.edu; Tue, 4 Jan 2000 01:27:05 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: not-2-disclose@the.net
Subject: MS-DOS Kermit, more capabalities
Message-ID: <010400011923not-2-disclose@the.net>
Date: Tue, 04 Jan 2000 06:26:59 GMT
Organization: Sympatico
To: kermit.misc@columbia.edu
Hi Frank,
Hi everybody,
MS> ...i'm a DOS_InterNet user... ...i looked for DOS INet FreeWare/
MS> ShareWare programs in hope that i'd get my hands on some piece of
MS> software which can be run even on a minimum setup, meaning: 8088
MS> 4,77 Mhz ~CPU~ 640 Kb ~RAM~ memory (512 Kb if possible!) No Hard
MS> Disk Two 5.25"/360 Kb diskette drives or a single 3.5"/720 Kb unit
MS> A crude 8250 ~UART~ serial-port A V.42Bis MoDem or better (i tied
MS> up an external 56K MoDem to a 8088!) DOS v3.3 (v3.0 compatibility
MS> would be fine but not required) I am trying to have some working
MS> `ZMoDem' and/or `Kermit' file transfer protocols for when accessing
MS> ~TelNet~ BBSes. To upgrade the hardware or to switch to protocols
MS> like ~FTP~/~HTTP~ *IS NOT* an option. `MS-Kermit v3.16' is the best
MS> thing i seen, so far. Most unfortunately, `Kermit' doesn't include
MS> the `ZMoDem' file transfer protocol (with control-character escaping
MS> & all)... Isn't there any MS-DOS `Kermit' update in preparation...
MS> ...since the latest `Win 9x' version already integrates the `ZMoDem'
MS> file transfer protocol, euh... would you happen to be aware of any
MS> project related to the development of a future MS-DOS `Kermit'
MS> version that will integrate the `ZMoDem' protocol as well? :^)
FDC> No. In Windows we do not have a 640K address-space limit. Anyway,
FDC> this is the *Kermit* Project.
Euh... "No", you don't happen to be aware of any project related to the
development of a future MS-DOS `Kermit' version that will integrate the
`ZMoDem' protocol? Or does it mean that the `Kermit' project droped its
DOS component? (Or `ZMoDem' is just a "bonus" feature for `Win' users?)
I'm sorry but i'm not sure what `Kermit' project is or is not, actually.
In any instance, can a user obtain the source-code of the latest/minimal
`Kermit' file transfer protocol (for inclusion into other programs)?...
MS> ...there's this "TOO MANY ACTIVE TAKE FILES AND MACROS" thing; i
MS> think i must be terminating macros incorrectly...
FDC> You can't expect a tiny program in a restricted memory space to be
FDC> able to do big things.
Big things?!! If it weren't for the lack of an integrated packet-driver
interface, an integrated ~TelNet~ protocol and a `Kermit' file transfer
protocol - in a program like `{Commo} v7.7' which uses less than 200 Kb
of ~RAM~ memory, in its actual form... and, considering its *VERSATILE*
macro language, euh... i guess that i'd have all i can dream of and i'd
be finished with implementing my On-Line ~NG~ reader in no time. `Conex
v7.5' happens to integrate all these things but one: it doesn't have a
comparable script/macro language... (At least, it has a half-acceptable
implementation of the `ZMoDem' protocol)... :o In short, I DON'T THINK
THAT THE SUM OF THE BEST FEATURES FOUND IN ALL THOSE PROGRAMS REQUIRES A
BLOATED EXECUTABLE... It's more like `Kermit' is complaining to me FOR
RUNNING ONE MACRO AFTER ANOTHER WITHOUT ME CLEARING THE UNUSED SPACE; i
can't but just wonder how i'm supposed to prevent that kind of build up!
As for what's supposed to be a "restricted memory space", i've looked at
a number of possible solutions and memory requirements depend on the DOS
pilot ~PPP~ software (it may vary by almost 100 Kb, from the best to the
worst case)... Amongst some others, i've noticed the driver files which
are found inside the Caldera `DR-WebSpyder' ShareWare archive, the Klos
`PPP-Share v1.4x' ShareWare archive and the `DOSPPPd v0.6 Beta' FreeWare
archive. The 1st 2 packages both happen to be compatible with Novell's
`NetWare' DOS ~ODI~ environment; `EPPPD'/`DOSPPPd' emulates the popular
`EtherNet'/Class-1 ~WatTCP~ interface. Both interfaces are supported by
`Kermit v3.14+', the `NetWare' suite is the less memory-hungry of all...
Klos's ~PPP~ pilot is slightly bigger but it appeared to allow for 10 %
faster D/L rates. :) `EPPPD' isn't bad; only, that one once gave me a
tough time when i tried to run it on a machine where there was an ~IRQ~
conflict. Also, when it comes to using it on an `XT's which are equiped
with only a 8250 ~UART~, Klos `PPP' can be as bad as `EPPPD'... I don't
know how the `NetWare' suite behaves in presence of a 8250 because the
8088 on which i made the test had an internal MoDem with its own 16550.
Euh... Anyway. %*o Overall, memory consumption is approximately like
this - from the lightest to the heaviest:
LSL.COM (21/28 Kb), NCOMX.COM (11/12 Kb), NWRemote.COM (21/26 Kb).
EPPPD.EXE (66 Kb).
LSL.COM (21/28 Kb), Klos PPP.EXE (57/63 Kb).
Moreover, when you consider that i'm conducting my preliminary `Kermit'
macro tests on a 386 equiped with ~XMS~ memory management, euh... and
considering that i still have some 260 Kb left of free ~RAM~ memory when
i type "Run Mem" at the `Kermit' command-line, euh... 8-o
Frankly, it's quite hard to see how i'd be in need of more memory here!!
If i may, i have this persistent impression that my problem comes from
within! - after `Kermit' has been loaded; following a limited number of
macro-key presses!... %-o Each time i run one of my macros some more
memory is being gobled up and i just don't know how it can be released.
Help!
[...]
Again. Thanks for your attention reading me. :)
Michel Samson